chore(release): sync main to published v2.58.0 - #1146
Merged
Conversation
(cherry picked from commit d089164)
|
This pull request is automatically built and testable in CodeSandbox. To see build info of the built libraries, click here or the icon next to each commit SHA. |
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1146 +/- ##
=======================================
Coverage 84.97% 84.98%
=======================================
Files 1230 1230
Lines 21542 21542
Branches 8185 8185
=======================================
+ Hits 18306 18307 +1
+ Misses 3150 3149 -1
Partials 86 86 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
v2.58.0was tagged and published to npm on 2026-07-07 (by Amol Samota), but itschore(release): 2.58.0bump commit was never merged intomain. As a resultmain'spackage.jsonwas stale at2.57.9— behind the live npm version.This blocks any further release:
standard-versionrun frommainwould cut2.57.10(lower than the published2.58.0) — a version regression.What
Cherry-picks the original
2.58.0bump commit (d0891640, authored by Amol) ontomain:package.json:2.57.9→2.58.0CHANGELOG.md: adds the2.58.0entry (matches what was published)No source/runtime files touched — disjoint from the Revert #1138 already on
main.Safety
v*tag push;v2.58.0already exists. Merging this PR does not tag or publish anything.mainwith the already-shipped release.Follow-up
After this merges,
2.58.1(patch) will be cut to release the pendingRevert "fix(Upload)..." (#1138)that currently sits onmainunreleased.